Consolidated network repository (cnr)

ABSTRACT

The disclosed subject matter relates to an architecture that can facilitate support for or integration of disparate communications networks. The architecture can embody a consolidated network repository (CNR) that can be configured as a single logical repository that can potentially be configured according to a common schema regardless of the type or number of schema employed by the disparate communications networks.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/159,674, filed Mar. 12, 2009, entitled “CONSOLIDATED NETWORKREPOSITORY (CNR).” The entirety of this application is incorporatedherein by reference.

BACKGROUND

Today, there are many types of communications networks that cater todifferent needs of subscribers or compete for subscribers acrossplatforms. Some examples include wireless communications networks,wireline communications networks, Internet Protocol (IP) MultimediaSubsystem (IMS) communications networks, broadband communicationsnetworks, and so on. Many providers exist in the market today that offerservices for more than one type of communication network, thus, it couldbe beneficial to such providers to integrate or converge the variousnetworks into a single platform.

However, conventional communications networks vary widely in terms ofimplementation, feature set, applications, or services. Generally, eachnetwork maintains an application-specific repository to store subscriberinformation, and each such repository typically operates according to adifferent schema.

SUMMARY

The following presents a simplified summary of the disclosed subjectmatter in order to provide a basic understanding of some aspects of thedisclosed subject matter. This summary is not an extensive overview ofthe disclosed subject matter. It is intended to neither identify key orcritical elements of the disclosed subject matter nor delineate thescope of the disclosed subject matter. Its sole purpose is to presentsome concepts of the disclosed subject matter in a simplified form as aprelude to the more detailed description that is presented later.

The subject matter disclosed herein, in one aspect thereof, comprises anarchitecture that can facilitate support for or integration of disparatecommunications networks. In accordance therewith and to other relatedends, the architecture can include a consolidated network repository(CNR) that can be configured as a single logical repository. The CNR canbe structured to in tiers or layers, thus including, e.g., a backendlayer that can physically store data, an interface layer that canoperate as a single point of integration for all data request, and adata management layer that can act as an intermediary between theinterface layer and the backend layer.

In more detail, the backend layer can physically house data associatedwith multiple disparate communications network platforms, which can bestored according to a common schema regardless of or independent of thesubscribing network platform's preferred or required schema. Theinterface layer can be configured to support multiple communicationsnetwork platforms, wherein the interface layer can receive a requestassociated with an access to the backend store. Further, the datamanagement layer can receive the request, access the backend layer, andserve the request.

In one or more aspects of the disclosed subject matter, the interfacecomponent can convert the received request from the application-specificformat designated by the platform originating the request to astandardized format expected by the data management layer. Hence, thedata management layer and the backend layer can be independent of anyprotocol or implementation of the originating platform, while theoriginating platform likewise need have no special knowledge of theinternal operation of the CNR.

The following description and the annexed drawings set forth in detailcertain illustrative aspects of the disclosed subject matter. Theseaspects are indicative, however, of but a few of the various ways inwhich the principles of the disclosed subject matter may be employed andthe disclosed subject matter is intended to include all such aspects andtheir equivalents. Other advantages and distinguishing features of thedisclosed subject matter will become apparent from the followingdetailed description of the disclosed subject matter when considered inconjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system that can facilitate support ofdisparate communications networks.

FIG. 2A depicts a block diagram of a system that illustrates an exampleof interface component in more detail.

FIG. 2B illustrates a block diagram of a system that depicts an exampledata management component in greater detail.

FIG. 2C is a block diagram of a system that provides an example of abackend store in more particular detail.

FIG. 3 illustrates a block diagram of a system that depicts adistributed CNR in discrete layers.

FIG. 4 is a block diagram of a system that illustrates various aspectsof an exemplary consolidated network repository.

FIG. 5 depicts a block diagram of a system that illustrates additionalfeatures or aspect of a consolidated network repository.

FIG. 6 illustrates a block diagram of a system that can perform or aidwith various determinations or inferences.

FIG. 7 is an exemplary flow chart of procedures that define a method forintegrating multiple disparate communications network platforms.

FIG. 8 depicts an exemplary flow chart of procedures defining a methodfor providing additional features or aspects in connection withintegrating multiple disparate communications network platforms.

FIG. 9 provides an exemplary flow chart of procedures defining a methodfor providing additional features or aspects in connection withintegrating multiple disparate communications network platforms within adistributed, layered CNR.

FIG. 10 illustrates an example wireless communication environment withassociated components that can enable operation of an enterprise networkin accordance with aspects described herein.

FIG. 11 illustrates a schematic deployment of a macro cell for wirelesscoverage in accordance with aspects of the subject specification.

FIG. 12 illustrates a block diagram of a computer operable to execute aportion of the disclosed architecture.

DETAILED DESCRIPTION

The disclosed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the disclosed subject matter. It may beevident, however, that the disclosed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the disclosed subject matter.

As used in this application, the terms “system,” “component,”“interface,” and the like are intended to refer to a computer-relatedentity or an entity related to an operational machine with one or morespecific functionalities. The entities disclosed herein can be eitherhardware, a combination of hardware and software, software, or softwarein execution. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, a program, and/or a computer. By wayof illustration, both an application running on a server and the servercan be a component. One or more components may reside within a processand/or thread of execution and a component may be localized on onecomputer and/or distributed between two or more computers. Thesecomponents also can execute from various computer readable media havingvarious data structures stored thereon. The components may communicatevia local and/or remote processes such as in accordance with a signalhaving one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network such as the Internet with other systemsvia the signal). As another example, a component can be an apparatuswith specific functionality provided by mechanical parts operated byelectric or electronic circuitry that is operated by software orfirmware application(s) executed by a processor, wherein the processorcan be internal or external to the apparatus and executes at least apart of the software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. An interface can include input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

Furthermore, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ),smart cards, and flash memory devices (e.g., card, stick, key drive . .. ). Additionally it should be appreciated that a carrier wave can beemployed to carry computer-readable electronic data such as those usedin transmitting and receiving electronic mail or in accessing a networksuch as the Internet or a local area network (LAN). Of course, thoseskilled in the art will recognize many modifications may be made to thisconfiguration without departing from the scope or spirit of thedisclosed subject matter.

As used herein, the terms “infer” or “inference” generally refer to theprocess of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources.

Further, terms like “user equipment,” “mobile station,” “mobile,”subscriber station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication service to receive orconvey data, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream. The foregoing terms are utilizedinterchangeably in the subject specification and related drawings.Likewise, the terms “access point,” “base station,” “cell,” “cell site,”and the like, are utilized interchangeably in the subject application,and refer to a wireless network component or appliance that serves andreceives data, control, voice, video, sound, gaming, or substantiallyany data-stream or signaling-stream from a set of subscriber stations.Data and signaling streams can be packetized or frame-based flows. It isnoted that in the subject specification and drawings, context orexplicit distinction provides differentiation with respect to accesspoints or base stations that serve and receive data from a mobile devicein an outdoor environment, and access points or base stations thatoperate in a confined, primarily indoor environment overlaid in anoutdoor coverage area. Data and signaling streams can be packetized orframe-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

Referring now to the drawing, with reference initially to FIG. 1, system100 that can facilitate support of disparate communications networks isdepicted. Generally, system 100 can include consolidated networkrepository

(CNR) 102 that can be configured as a single logical repository. Forexample, although CNR 102 can be single logical repository for data, CNR102 can be distributed throughout numerous storage devices or facilitiesas well as over multiple geographic regions, which is further detailedin connection with FIG. 3 infra.

CNR 102 can include backend store 104 that can maintain data associatedwith multiple disparate communications network or platform domains suchas component domains illustrated by reference numeral 106 and discussedfurther herein, or any other suitable domains or network platforms.Backend store 104 can be one or more physical storage devices orfacilities that can physically maintain data for various convergednetworks, such as data relating to subscribers to the various networksor the like. It should be appreciated that backend store 104 can beembodied as substantially any type of memory, including but not limitedto volatile or non-volatile, steady-state, sequential access, structuredaccess, or random access and so on. Additional detail relating tobackend store 104 can be found with reference to FIG. 2C.

Furthermore, CNR 102 can include interface component 108, which isfurther discussed in connection with FIG. 2A. However, briefly,interface component 108 can be configured to support multiplecommunications network platforms/domains (e.g., domains 106 . . . ),wherein interface component 108 can receive request 110 associated withan access to backend store 104. For example, the multiple communicationsnetwork platform/domains 106 can include all or a portion of wirelessdomain 112, wireline domain 114, an Internet Protocol (IP) MultimediaSubsystem (IMS) domain 116, a broadband domain 118, or any otherexisting or later developed network platform. Thus, interface component108 can support request 110 from third generation partnership project(3GPP) wireless network domains/platform as well as from 2G networks, 4Gnetworks, Long Term Evolution (LTE) networks, Evolved Packet System(EPS) networks, voice-over-IP (VOIP) networks, Internet queries and soon, as well as applications or services thereof.

Thus, in accordance with the described subject matter, a communicationsnetwork providers, for example, can converge multipleapplication-specific data stores for substantially any of a variety ofcommunications networks into a single data store (e.g., backend store104) that can increase reliability, speed, efficiency, redundancy, amongother features further discussed infra while maintaining scalability orextensibility and decreasing maintenance or implementation costs.Moreover, converging multiple network domains can provide more robustcapabilities for intra-network operation, and can be an importantfeature for subscribers.

In accordance with the above-mentioned benefits, subscriber data (orother data included in backend 104) can be harmonized across themultiple network platforms/domains 106 into one logical data layer,which can mitigate data inconsistencies and/or unnecessary dataduplications. Furthermore, by employing only a single logical database(e.g., backend 104), only one point of integration (e.g., interfacecomponent 108) need be exposed for all applications, which cansignificantly simplify subscriber and service provisioning or upkeep.Moreover, wasted network capacity can be reduced or eliminated bystandardizing/consolidating network architecture, which can reduceserver and storage requirements as well as sub-optimal usage of, e.g.,database software licenses. In addition, the ability to share suchresources can save on energy costs, floor space, or operations, and canreduce administration and management/maintenance (OA&M) costs, e.g., bycentralizing expertise or other resources. Still another benefit can besimplified or more expedient implementation or roll out for additionalor future networks or services, which can be more readily integratedwith an existing CNR.

As noted previously, interface component 108 can operate as a singlepoint of integration for multiple communications network platforms 106or any application or service thereof. Accordingly, interface component108 can support substantially any type of request 110 regardless of thetype or purpose or from which platform 106 or application request 110originates. For example, interface component 108 can support request 110from a wireless switch, from a social networking site or service, or a9-1-1 call. In other words, interface component 108 can mimic anypotential application interface such as 3GPP or lightweight directoryaccess protocol (LDAP). Hence, other or existing portions of acommunications network (e.g., platforms 106) need have no specialknowledge of the structure, operation, or behavior of CNR 102, butrather can behave as though accessing its own associated database.

Thus, regardless of the type or nature of request 110, interfacecomponent 108 can handle request 110 as well as an appropriate action orresponse. In one or more aspect of the disclosed subject matter, suchcan be accomplished by including in interface component 108 multiplefrontend interfaces that can facilitate support of the multipleplatforms/domains 106. For example, a disparate frontend for eachsupported platform 106 or application can be included in interfacecomponent 108, which is further detailed in connection with FIG. 2A.

In addition, CNR 104 can further include data management component 120,which is discussed in more detail with reference to FIG. 2B. Datamanagement component 120 can receive the request (or an abstraction ofthe request), and then access backend store 104 in order to serve therequest, which can be forwarded to the requestor by interface component108. It should be appreciated that due to a wide range of potentialtypes or protocols for request 110, in one or more aspect, interfacecomponent 108 can convert request 110 to standardized request 124formatted according to a standard interface protocol expected by datamanagement component 120. Hence, data management component 120 need haveno special knowledge of the platform 106 that initiates request 110 orany protocol or application thereof. Rather, standardized request 124can be abstracted according to a desired schema, potentially customizedfor backend store 104. Upon retrieving the appropriate data (or otherresults) from backend 104, data management component 120 can transmit astandardized response 124 to interface component 108. Interfacecomponent 108 can then reverse the abstractions performed on request 110when converting to standardized request 124 to construct response 122(in the format or protocol expected by the domain which initiatedrequest 110) from standardized response 126. Additionally oralternatively, response 122 can be constructed by data managementcomponent 120 (e.g., by a data adaption function component detailedinfra with reference to FIG. 2B), forwarded to interface component 108and/or delivered to the request initiator.

Turning now to FIG. 2A, system 200 illustrates an example of interfacecomponent 108 in more detail. As previously discussed, request 110 canbe received from an element of one or more domain 106 and response 122can be returned to that element. In either case, the request 110 orresponse 122 can be domain- or application-specific. Likewise, request110 can be converted from domain-specific to standardized request 124,while standardized response 126 can be translated to a domain- orapplication-specific response 122.

As further noted above, interface component 108 can include multiplefrontend interfaces, four examples of which are depicted here, althoughit should be appreciated that substantially any number of additionalfrontend interfaces can be included in interface component 108 orextended after initial implementation. In particular, interfacecomponent 108 can include any or all of Home Location Register (HLR)frontend 202, Home Subscriber Server (HSS) frontend 204, Authentication,Authorization, and Accounting (AAA) frontend 206, application interfacefrontend 208, as well as other suitable frontends, all or a portion ofwhich can be data-less frontends.

In more detail, HLR frontend 202 can employ Mobile Application Part(MAP) protocol to facilitate an interface to network elements configuredaccording to a wireless domain 112 communication standard. Thus, one ormore HLR frontend 202 can support various wireless-based protocols orapplications for interface component 108. On the other hand, HSSfrontend 204 can employ DIAMETER protocol to facilitate an interface tonetwork elements configured according to an IMS domain 116 communicationstandard. Hence, one or more HSS frontend 204 can support variousIMS-based protocols or applications for interface component 108.

Similarly, AAA frontend 206 can employ either DIAMETER or RemoteAuthentication Dial In User Service (RADIUS) protocol to facilitate aninterface to network elements that utilize one or more AAA-basedapplication, while application interface frontend 208 can be configuredto support at least one of AAA, Equipment Identity Register (EIR),Common Architecture for Real-Time Services (CARTS), LightweightDirectory Access Protocol (LDAP), Application Server (AS), or the like.Appreciably, as briefly discussed supra, the illustrated as well as anyother suitable frontend can be data-less, however, such is notnecessarily a requirement.

Moreover, in one or more aspects of the disclosed subject matter, themultiple frontends (e.g., 202-208 . . . ) can be configured to supportprotocols including at least one of C, D, Cx, Dx, LDAP, Simple ObjectAccess Protocol (SOAP), Extensible Markup Language (XML), HypertextTransfer Protocol (HTTP), Simple Network Management Protocol (SNMP) andso forth, as well as N+K redundancy.

Referring now to FIG. 2B, system 210 depicts an example data managementcomponent 120 in greater detail. Data management component 120 canfacilitate serving request 110 as substantially described supra. Giventhat request 110 can relate to retrieval of, e.g., subscriber profileinformation from backend store 104, data management component 120 willtypically be responsible for keeping track of where in backend store 104requested data resides. Hence, in one or more aspects, data managementcomponent 120 can be configured to maintain location index 212, whichcan describe the location within backend store 104 of requested data.

In addition, in one or more aspect, data management component 120 canfurther include any or all of indexing component 214 (for which locationindex 212 can be portion), routing component 216, caching component 218,data adaption function (DAF) component 220, notification component 222,SuM component 224 as well as other suitable components or modules. Byway of illustration, at least one of indexing component 214 or routingcomponent 216 can be configured to maintain location index 212 or tooperate as a subscriber directory for all or a portion of frontendsincluded in interface component 108.

Caching component 218 can be configured to temporarily store dataretrieved from the backend store, which can be efficiently re-accessedin order to, e.g., reduce traffic to backend store 104 and/or tominimize response delay or latency for CNR 102. Caching component 218can be employed for caching information available to mobile ornon-mobile networks, network management systems or the like. Forexample, data can be cached in response to request(s) for a data elementor request(s) for an update to a data element and in accordance with acache retention protocol. Request(s) (e.g., request 110) for a dataelement of an update to a data element can be received from a set ofexternal networks, mobile or otherwise, that can interface a protocollayer. The protocol layer can include various signaling protocolsassociated with various network components or services, or applicationdata. The protocol layer can also deliver the request(s) to a datamanagement layer in a format compatible with the source/originator(network component, application server, etc.) of the request(s). A datamanagement layer (e.g., comprised of multiple data management components120, detailed infra) can format such requests in accordance with apredetermined signaling protocol and can further allow caching, as wellas other data storage functionality in accordance with the predeterminedprotocol. The data management layer can be functionally coupled to abackend storage layer (e.g., comprised of multiple backend stores 104,discussed infra), which can be a distributed, heterogeneous data storagelayer. The backend storage layer can include all or substantially allnetwork data that can be accessed or generated by network components orapplication servers that can access the protocol layer or an interfacelayer (e.g., comprised of multiple interface components 108, detailedinfra). In addition, backend storage layer also can include data relatedto network management systems, and components therein; such systemsfunctionally coupled to the data manager layer.

With respect to caching, the cache retention can establish a versioningprotocol and a set of timers that determine a period to elapse prior toremoval of a version of the cached data element. In addition, a masterrecord of a data element can be updated with a most recent version ofcached data element if a retention timer expires. Updates to a cacheddata element can be effectuated if an integrity assessment determinesthat recordation of an updated version of the data element preservesoperational integrity of one or more network components or services. Theassessment can be based on integrity logic that establishes a set ofrules that evaluate operational integrity of a requested update to adata element. Retention protocol and integrity logic are configurable; anetwork component can supply a configuration or such configuration canbe effected autonomously.

DAF component 220 can be configured to adapt data retrieved from backendstore 104 for data structures or data representations expected by anapplication that originated request 122. Accordingly, DAF component 220can, e.g., simplify integration of existing repositories into a commondata model or schema. Likewise, notification component 222 can beconfigured to support subscribe or notify mechanisms in order to, e.g.,allow one or more of the multiple frontend interfaces included ininterface component 108 of changes to data included in backend store104. Last to be described, data management component 120 can alsoinclude SuM component 124, which can be configured to interface toprovisioning components or to coordinate updates associated with CNR102. Appreciably, data management component 120 can include othersuitable components as well.

Referring briefly to FIG. 2C, system 230 provides an example of backendstore 104 in more particular detail. For example, as depicted, backendstore 104 can include multiple physical data repositories 232 in orderto, e.g., redundantly store all or portions of data associated with themultiple disparate communications network platforms 106. As introducedabove, it should be appreciated that backend store 104 can be configuredwith a single, common schema, which can greatly simply accesses and makefor a much more robust system than, e.g., merely merging multiplerepositories of individual networks, all with distinct schema.Accordingly, standardized request 124 and standardized response 126transmitted to or received from data management component 120 can beformatted according to this common schema.

Hence, backend store 104 can provide permanent storage for CNR 102 datain redundant data repositories 232. Therefore, any data entity or entrycan be stored in two or more data repositories 232. Moreover, datarepositories 232 can be distributed over two or more sites and datarepositories 232 can be replicated on several servers in differentlocations in order to provide geo-redundancy. For example, replicationacross three servers can provide redundancy even when one of the serversis down due to maintenance or for another reason. All of the above canbe better appreciated with reference to FIG. 3. In addition, datarepositories 232 can be based on nonvolatile memory, volatile memory, ora combination thereof. Moreover, data included in data repositories 232can be partitioned either by a subscriber schema or a subset ofsubscriber schema in order to, e.g., provide robust scalability.Furthermore, it should be appreciated that in connection with components212-216 of FIG. 2B, the originator of request 110 need not have anyknowledge of which repository 232 a subscriber profile or otherrequested data is stored. Rather, such can be seamlessly andtransparently handled by data management component 120.

Turning now to FIG. 3, system 300 that depicts a distributed CNR indiscrete layers is provided. Although much of the above has beendirected toward a simplified conceptual CNR residing at a singlelocation, it should be understood that CNR 102 can comprise multipleinstances of the components detailed previously and span numerousgeographic regions even though CNR 102 can be organized as a singlelogical repository. For example, CNR 102 can include backend layer 302that can comprise multiple backend stores 104 ₁-104 _(N) (referred tohereinafter either individually or collectively as backend store(s)104), wherein N can be substantially any positive integer. Moreover, inone or more aspects, the backend stores 104 included in backend layer302 can be included in first logical wide area network (WAN) 304, e.g.,organized as a separate domain or network, potentially with each backendstore 104 as a peer to other backend stores 104. It should beappreciated that, depending upon the application for the disclosedsubject matter, backend layer 302 (as well as any other layer) can benetworked via a local area network (LAN) rather than by WAN 304. Suchcould be utilized, e.g., for applications or networks that cater tourban services or the like.

Similarly, CNR 102 can include interface layer 306, wherein interfacelayer 306 can include multiple interface components 108 ₁-108 _(O),wherein O can be substantially any positive integer. All or a portion ofinterface components 108 included in interface layer 306 can be includedin second logical WAN 308 (or a suitable LAN) and, thus, structured as aseparate or independent network or domain with respect to first logicalWAN 304. In addition, CNR 102 can further comprise data management layer310 that can include multiple data management components 120 ₁-120 _(P),wherein P can be substantially any positive integer. Appreciably,positive integers N, O, and P can be, but need not be, equal, as will befurther detailed below. Moreover, as with backend layer 302 andinterface layer 306, data management layer 310 can be organized as adisparate logical WAN, network, or domain, in particular as thirdlogical WAN 312.

In accordance with the above, it should be readily apparent that CNR 102can be physically distributed among multiple geographic locations,wherein at least a first portion of one or more layers (e.g., layers302, 306, 310) included in CNR 102 can reside at a first geographiclocation, say location/region A (denoted by reference numeral 314) andat least a second portion of the one or more layers included in CNR 102can reside at a second geographic location, e.g., location/region X(labeled with reference numeral 316. Thus, each geographic location orsite (e.g., locations 314, 316, . . . ) can include all or a portion ofthe elements of system 100 discussed in connection with FIGS. 1-2C, orin some case multiple instances of such elements (e.g., as depicted withrespect to location 316).

In accordance with the above, it is apparent that interface layer 306can consist of multiple frontends which can provide a single point ofaccess to CNR 102 whether interfacing to 2G, 3G, EPS, IMS networkelements or other applications like AAA MIND, Common Architecture forReal-Time Services (CARTS), AS or the like. Moreover, as noted supra,these frontends can be data-less, and thus emulate or appear, e.g., as aHLR to mobility wireless domains, as an IMS HSS to IMS networks, or asan application repository to schema evolution through an extensible,re-usable and flexible framework (SERF) layer. Hence, CNR 102 orportions thereof can be implemented as though it were a legacy HLR orIMS HSS without any major changes in the subject network given therobust support for substantially any interface, standard or otherwise.

Likewise, backend layer 302 can be where all or a portion of datamanaged by CNR 102 is physically stored. Data repositories 232associated with backend layer 302 can be physically distributed acrossvarious regions of a service provider's network, where actual data isstored and/or replicated. Hence, the number of subscribers as well asportions of one or more subscribers' data can be flexibly distributed tomeet various partitioning requirements. For example, by limiting thenumber of subscribers for any one data repository 232, server load canbe architected according to expectation as part of CNR 102implementation or design. Moreover, load balancing or data locationoptimization can be effectively accomplished in as well.

In one or more aspects of the disclosed subject matter, the multiplebackend stores included in backend layer 302 can be networked via firstlogical WAN 304 such that a particular backend store 104 included inbackend layer 302 can be configured to communicate with other backendstores 104 in a horizontal fashion via first logical WAN 304 or with anassociated data management component 120 in a vertical fashion.Similarly, multiple interface components 108 included in interface layer306 can be networked via second logical WAN 308 such that a particularinterface component 108 included in the interface layer 306 can beconfigured to communicate with other interface components 108 in ahorizontal fashion via second logical WAN 308 or with an associated datamanagement component 120 in a vertical fashion. Furthermore, multipledata management components 120 included in the data management layer 310can be networked via third logical WAN 312 such that a particular datamanagement component 120 included in data management layer 312 can beconfigured to communicate with other data management components 120 in ahorizontal fashion via third logical WAN 312 or with an associatedinterface component 108 or an associated backend store 104 in a verticalfashion.

It should be understood that communicating in a horizontal fashion isillustrated by reference numeral 318 for enabling, e.g., any or allelements within a layer of CNR 102 to communicate with other likeelements over the associated logical WAN, e.g., by way of peer-to-peercommunication. Accordingly, updates to one of the elements (e.g., one ofthe interface components 108 within interface layer 306, etc.) can bepropagated to other like elements via the associated logical WAN. Thus,it should be appreciated that, in accordance with one or more aspects ofthe disclosed subject matter, at least one layer included in CNR 102 canbe configured to be independently extensible or updateable such that anextension or update to the at least one layer need not require anyassociated extension or update to other layers included in CNR 102.

Similarly, communicating in a vertical fashion is depicted by referencenumeral 320 and can relate to communication among elements within asingle geographic location, region, or site, such as location 314, 316,and so on. Moreover, while location 314 is depicted with exactly oneelement in each layer (e.g., one interface component 108 in interfacelayer 306, one data management component 120 in data management layer310 . . . ) whereas location 316 is illustrated to include multipleelements for each layer, it should be understood that a given site isnot necessarily restricted to such topology. For example, a givenlocation or site can include substantially any number of elements withina particular layer independent of the number of elements in anotherlayer. Furthermore, in addition to the redundancy of data repositories232 within a particular site introduced supra, redundancy can also beoffered between regions should a particular region become unreachablebecause of some catastrophic issue, for example.

With the foregoing in mind, it can be readily appreciated that thedisclosed subject matter can provide numerous advantages for existingcommunications networks or for consolidating or converging multiplenetworks whether existing or subsequently rolled out. For example, CNR102 can, in general, provide a single logical repository for all dataassociated with all integrated networks. CNR 102 can be distributed forready scalability or enhanced performance, as well as load balancedinternally with local and geographical redundancy and/or robust faultresilience or fault recovery.

With respect to data interfaces (e.g., interface component 108 orinterface layer 306) associated with CNR 102, all such interfaces can bescalable and independent of data storage architecture, with the abilityto add new interfaces for ready extensibility. The interfaces can alsosupport or promote standards-based elements or protocols, and supportany such protocols that are targeted, such as, e.g., IMS HSS/SLF andmobility HLR, LDAP, IPv4, IPv6, and so on.

Regarding data storage (e.g., backend store 104, backend layer 302, datarepositories 232), such storage can be independent of the data interfacearchitecture. Additionally, given the ready extensibility of CNR layers,geographic distribution, and logical mapping, data storage need have noinherent capacity limit. In addition, CNR 102 can provide support fordata synchronization and protection of data integrity and/orreliability. Furthermore, given that data storage can be according to asingle common schema, the schema can be standardized and published, yetremain flexible and configurable to, e.g., support independentapplication schemas.

With respect to application support, CNR 102 can provide the ability toconsolidate existing mobility, BVoIP, and/or CVoIP applications datarepositories. Moreover, CNR 102 can remain extensible to support futureapplications such as, e.g., World Wireless Congress (WWC) as well aspotentially any existing service or support required by regulatoryagencies, such as E911, CALEA, NS/EP, LNP, WPS NPA splits, and so forth.

Furthermore, CNR 102 can provide robust security options as well. Forinstance, backend stores 104 and/or repositories 232 can be resident ina trusted domain, wherein access can be limited only to elements withinthe trusted domain. Additionally, data protection relating to, e.g.,stored credentials, one-way encryption, or the like, can be enforced anddata transmission can be facilitated in accordance with ASPRs.

With reference now to FIG. 4, system 400 illustrates various aspects ofan exemplary consolidated network repository. Appreciably, the depictedconsolidated network repository can be substantially similar to thatdetailed supra. For example, the consolidated network repository caninclude frontend interface layer 402, data management layer 404, andbackend repository layer 406, similar to that which was previouslydescribed. Typical communication networks 408 and the CommonArchitecture for Real-Time Services (CARTS) 410 can access the CNRthrough frontend interface layer 402. System 400 can also includeprovisioning component 412 and element management component 414, whichcan relate to accessing the consolidated network repository through datamanagement layer 404.

Frontend interface layer 402 can represent a boundary between theconsolidated network repository and the various disparate networks 408or associated applications (as well as CARTS 410) requiring the servicesprovided by the consolidated network repository. Moreover, frontendinterface layer 402 can pass all data to the lower layers for processingand therefore can be a data-less interface layer. Frontend interfacelayer 402 can also provide interfaces matching existing network datainterfaces, hence enabling consolidated network repository integrationinto a present network as if it were legacy support for existingdatabase systems.

Further, data management layer 404 can receive requests from, or returnsresponses to, frontend interface layer 402 on one side or submitsrequests, or receives responses from, backend repository layer 406 onthe other side. Data management layer 404 can provide necessaryfunctionality such as but not limited to indexing of data, data caching,application request translation, such as to the lightweight data accessprotocol (LDAP), and subscriber management. The design of theconsolidated network repository can enable data management layer 404 toreceive a request for data access with advanced knowledge of thelocation of the database holding the requested data without any frontend processing. Such can be based on, e.g., the physical location of thesubscriber, the service or application originating the request, or thelocation of any other related data stored in the consolidated networkrepository.

Additionally, data management layer 404 can provide a direct interfaceto the provisioning applications 412 or the element managementapplications 414. Providing such lower level interface to theconsolidated network repository can allow for simpler provisioning, agreater level of redundancy, or overall resilience to the consolidatednetwork repository architecture. Further, data management layer 404 canalso provide for a common data schema by incorporating the schemas ofHLR, HSS, or other application servers (AS) into the common data schema.

In one or more aspects of the disclosed subject matter, backendrepository layer 406 can be the physical storage location for allnetwork and application data. The backend layer 406 repositories can bedistributed across all or a portion of regions of the network, therebyproviding for localized storage, potentially with the constraints ofmultiple and different localized implementations. In one or moreaspects, the distributed localized storage can provide for faster ormore efficient access to the localized data without necessarily limitingperformance of the consolidated network repository or access by remotesubscribers. Moreover, potentially any limitations enforced on existingstorage systems, such as the number of subscribers per repository can beenforced by the localized storage of the consolidated networkrepository, if desired. Further, backend repository layer 406 can beredundant as detailed supra, and can be implemented as one or more pairsof storage devices providing either or both geographical or internalredundancy.

In one or more aspects, each layer of the consolidated networkrepository 400 can be located within the same wide area network (WAN),thereby making peer to peer communication possible. Such a feature canenable the different layered nodes to communicate with each other andperform tasks such as load balancing or data location optimization. Forexample, consider a subscriber changes residences from one locality toanother. The consolidated network repository can detect the fact thatthe subscriber has relocated and automatically transfer the subscriber'sprofile or other data to the new more proximate data repository.Appreciably, in such cases, time constraints, such as thirty days in thenew location, can be configured to prevent data transfers for temporarymoves such as travel or visitations.

Referring now to FIG. 5, system 500 illustrates additional features oraspect of a consolidated network repository. In particular, consolidatednetwork repository 502 is depicted interacting with a common customerprofile (CCP) enabler 504 and CCP synchronization services 506. Theconsolidated network repository 502 can provide support for third partycustomer applications to maintain subscriber application data inconsolidated network repository 502 while also potentially providing allthe previously described benefits detailed herein. Further, customerprofile provisioning and maintenance systems can be provided access to,but prevented from interacting with application data associated withother customers.

Furthermore, as will be appreciated, various portions of the disclosedsystems above and methods below may include or consist of artificialintelligence or knowledge or rule based components, sub-components,processes, means, methodologies, or mechanisms (e.g., support vectormachines, neural networks, expert systems, Bayesian belief networks,fuzzy logic, data fusion engines, classifiers . . . ). Such components,inter alia, and in addition to that already described herein, canautomate certain mechanisms or processes performed thereby to makeportions of the systems and methods more adaptive as well as efficientand intelligent.

It should be further appreciated that the methodologies disclosedthroughout this specification are capable of being stored on an articleof manufacture to facilitate transporting and transferring suchmethodologies to computers. The term article of manufacture, as used, isintended to encompass a computer program accessible from anycomputer-readable device, media, or a carrier in conjunction with suchcomputer-readable device or media.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, industrial controllers and the like,each of which can be operatively coupled to one or more associateddevices.

The illustrated aspects of the claimed subject matter can also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and non-volatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media includes both volatileand non-volatile, removable and non-removable media implemented in anymethod or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalvideo disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Suitable combinationsof the any of the above should also be included within the scope ofcommunication media derived from computer-readable media and capable ofsubsequently propagating through electrically conductive media, (e.g.,such as a system bus, microprocessor, data port, and the like) and/ornon-electrically conductive media (e.g., in the form of radio frequency,microwave frequency, optical frequency and similar electromagneticfrequency modulated data signals).

Now turning to FIG. 6, system 600 that can perform or aid with variousdeterminations or inferences is illustrated. Generally, system 600 caninclude one or more interface component 108 and/or one or more datamanagement component 120, each as substantially described herein. Inaddition to what has been described, the above-mentioned components canmake intelligent determinations or inferences. For example, Bayesianprobabilities or confidence measures can be employed or inferences canbe based upon machine learning techniques related to historicalanalysis, feedback, and/or previous determinations or inferences. Forinstance, interface component 108 can intelligently determine or inferconversion techniques when generating standardized request 122 basedupon application-specific request 110. In addition, data managementcomponent 120 can intelligently determine or infer optimal or efficientload balancing or data location management.

In addition, system 600 can also include intelligence component 602 thatcan provide for or aid in various inferences or determinations. Inparticular, in accordance with or in addition to what has been describedsupra with respect to intelligent determinations or inferences providedby various components described herein, e.g., all or portions ofinterface component 108 or data management component 120. Additionallyor alternatively, all or portions of intelligence component 602 can beincluded in one or more components described herein.

Moreover, intelligence component 602 will typically have access to allor portions of data sets described herein, such as data store 604. Asused herein, data store 604 is intended to be a repository of all orportions of data, data sets, or information described herein orotherwise suitable for use with the described subject matter, which caninclude data resident in backend stores 104. Data store 604 can becentralized, either remotely or locally cached, or distributed,potentially across multiple devices and/or schemas. Furthermore, datastore 604 can be embodied as substantially any type of memory, includingbut not limited to volatile or non-volatile, steady-state, sequentialaccess, structured access, or random access and so on. It should beunderstood that all or portions of data store 604 can be included insystem 100, or can reside at least in part remotely from system 100.

Accordingly, in order to provide for or aid in the numerous inferencesdescribed herein, intelligence component 602 can examine the entirety ora subset of the data available and can provide for reasoning about orinfer states of the system, environment, and/or user from a set ofobservations as captured via events and/or data. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states, for example. The inference can beprobabilistic - that is, the computation of a probability distributionover states of interest based on a consideration of data and events.Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data.

Such inference can result in the construction of new events or actionsfrom a set of observed events and/or stored event data, whether or notthe events are correlated in close temporal proximity, and whether theevents and data come from one or several event and data sources. Variousclassification (explicitly and/or implicitly trained) schemes and/orsystems (e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, data fusion engines . . . ) canbe employed in connection with performing automatic and/or inferredaction in connection with the disclosed subject matter.

A classifier can be a function that maps an input attribute vector,x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to aclass, that is, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. A support vector machine(SVM) is an example of a classifier that can be employed. The SVMoperates by finding a hyper-surface in the space of possible inputs,where the hyper-surface attempts to split the triggering criteria fromthe non-triggering events. Intuitively, this makes the classificationcorrect for testing data that is near, but not identical to trainingdata. Other directed and undirected model classification approachesinclude, e.g., naive Bayes, Bayesian networks, decision trees, neuralnetworks, fuzzy logic models, and probabilistic classification modelsproviding different patterns of independence can be employed.Classification as used herein also is inclusive of statisticalregression that is utilized to develop models of priority.

FIGS. 7-9 illustrate various methodologies in accordance with thedisclosed subject matter. While, for purposes of simplicity ofexplanation, the methodologies are shown and described as a series ofacts, it is to be understood and appreciated that the disclosed subjectmatter is not limited by the order of acts, as some acts may occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers. The term article ofmanufacture, as used herein, is intended to encompass a computer programaccessible from any computer-readable device, carrier, or media.

Referring now to FIG. 7, exemplary method 700 for integrating multipledisparate communications network platforms is depicted. Generally, atreference numeral 702, a CNR can be configured as a single logicalrepository for multiple disparate communications networks. In accordancetherewith, at reference numeral 704, one or more physical storagedevices or facilities can be employed as a backend layer for the CNR. Inparticular, the CNR and/or the backend store(s) or layer can includesubstantially any number of physical drives or storage devices and canbe geographically distributed as detail herein.

At reference numeral 706, the backend layer can be configured formaintaining data associated with the multiple disparate communicationsnetwork domains. Appreciably, such data when existing in disparatenetworks can stored in a wide variety of schema according to theimplementation of those disparate networks, yet such need not be thecase with the CNR.

Likewise, at reference numeral 708, an interface layer for the CNR canbe configured for supporting access requests from the multiple disparatecommunications network domains. Such access request can also span a widerange of protocols, service features, and/or applications. Hence, theinterface can potentially be configured to handle or support any or allthe protocols or applications desired.

In addition, at reference numeral 710, a data management layer thatoperates as an intermediary between the interface discussed inconnection with reference numeral 708 and the backend layer detailed atreference numeral 706. At reference numeral 712, a request associatedwith an access to the backend store can be received at the interfaceand, typically, forwarded to the data management component.

Turning now to FIG. 8, exemplary method 800 for providing additionalfeatures or aspects in connection with integrating multiple disparatecommunications network platforms is depicted. For example, at referencenumeral 802, the request received at integrating multiple disparatecommunications network platforms 712 of FIG. 7 can be converted to astandardized request according to a standard protocol expected by thedata management component. Appreciably, the standardized protocol can beindependent of a domain or application type that originated the request.

At reference numeral 804, the CNR can be configured as the singlelogical repository for two or more of a wireless domain, a wirelinedomain, an IMS domain, or a broadband domain. It should be understoodthat CNR can support other domains as well, with the aforementioneddomains intended to serve as concrete examples. At reference numeral806, multiple frontends can be included into the interface, wherein suchfrontends can be, respectively, adapted for interfacing with themultiple disparate communications network domains or applicationsassociated therewith.

Regarding reference numeral 808, the data management component can beutilized for maintaining a location index for data included in thebackend store. Accordingly, the data management component can beapprised at any given time of the location of subscriber profiles orother data. Whereas at reference numeral 810, the backend store can beconfigured with a single, common schema. As such, the data in the backedstore can be accessed or recalled potentially much more efficiently thanif many schemas existed.

With reference now to FIG. 9, exemplary method 900 for providingadditional features or aspects in connection with integrating multipledisparate communications network platforms within a distributed, layeredCNR is provided. At reference numeral 902, the CNR can be distributedover multiple geographical regions, yet can still retain a logicalmapping as a single data store.

At reference numeral 904 at least one backend store can be included inthe multiple geographical regions and associated with a first logicalWAN that networks the backend layer detailed in connection withreference numeral 702, wherein each backend store distributed over themultiple geographical regions can be connected in peer-to-peer fashion.Likewise, at least one interface component can be included in themultiple geographical regions and associated with a second logical WANthat networks the interface layer of reference numerals 704 and 706.Furthermore, at least one data management component can be included inthe multiple geographical regions and associated with a third logicalWAN that networks the data management layer discussed in connection withreference numeral 710.

At reference numeral 906, at least one layer (e.g., the interface layer,the data management layer, or the backend layer) of the CNR can beconfigured for communicating in a horizontal manner via a single logicalWAN (e.g., the first, second, or third logical WAN), or in a verticalmanner with one or more disparate layer at a same geographical region.Last to be described, at reference numeral 908, the at least one layercan be configured for independent extensibility or updateability.

To provide further context for various aspects of the subjectspecification, FIG. 10 illustrates an example wireless communicationenvironment 1000, with associated components that can enable operationof a femtocell enterprise network in accordance with aspects describedherein. Wireless communication environment 1000 includes two wirelessnetwork platforms: (i) A macro network platform 1010 that serves, orfacilitates communication) with user equipment 1075 via a macro radioaccess network (RAN) 1070. It should be appreciated that in cellularwireless technologies (e.g., 4G, 3GPP UMTS, HSPA, 3GPP LTE, 3GPP UMB),macro network platform 1010 is embodied in a Core Network. (ii) A femtonetwork platform 1080, which can provide communication with UE 1075through a femto RAN 1090, linked to the femto network platform 1080through a routing platform 102 via backhaul pipe(s) 1085, whereinbackhaul pipe(s) are substantially the same a backhaul link 3853 below.It should be appreciated that femto network platform 1080 typicallyoffloads UE 1075 from macro network, once UE 1075 attaches (e.g.,through macro-to-femto handover, or via a scan of channel resources inidle mode) to femto RAN.

It is noted that RAN includes base station(s), or access point(s), andits associated electronic circuitry and deployment site(s), in additionto a wireless radio link operated in accordance with the basestation(s). Accordingly, macro RAN 1070 can comprise various coveragecells like cell 1205, while femto RAN 1090 can comprise multiple femtoaccess points. As mentioned above, it is to be appreciated thatdeployment density in femto RAN 1090 is substantially higher than inmacro RAN 1070.

Generally, both macro and femto network platforms 1010 and 1080 includecomponents, e.g., nodes, gateways, interfaces, servers, or platforms,that facilitate both packet-switched (PS) (e.g., internet protocol (IP),frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS)traffic (e.g., voice and data) and control generation for networkedwireless communication. In an aspect of the subject innovation, macronetwork platform 1010 includes CS gateway node(s) 1012 which caninterface CS traffic received from legacy networks like telephonynetwork(s) 1040 (e.g., public switched telephone network (PSTN), orpublic land mobile network (PLMN)) or a SS7 network 1060. Circuitswitched gateway 1012 can authorize and authenticate traffic (e.g.,voice) arising from such networks. Additionally, CS gateway 1012 canaccess mobility, or roaming, data generated through SS7 network 1060;for instance, mobility data stored in a VLR, which can reside in memory1030. Moreover, CS gateway node(s) 1012 interfaces CS-based traffic andsignaling and gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, gateway node(s) 1018 can be embodied in gateway GPRS supportnode(s) (GGSN).

In addition to receiving and processing CS-switched traffic andsignaling, gateway node(s) 1018 can authorize and authenticate PS-baseddata sessions with served (e.g., through macro RAN) wireless devices.Data sessions can include traffic exchange with networks external to themacro network platform 1010, like wide area network(s) (WANs) 1050; itshould be appreciated that local area network(s) (LANs) can also beinterfaced with macro network platform 1010 through gateway node(s)1018. Gateway node(s) 1018 generates packet data contexts when a datasession is established. To that end, in an aspect, gateway node(s) 1018can include a tunnel interface (e.g., tunnel termination gateway (TTG)in 3GPP UMTS network(s); not shown) which can facilitate packetizedcommunication with disparate wireless network(s), such as Wi-Finetworks. It should be further appreciated that the packetizedcommunication can include multiple flows that can be generated throughserver(s) 1014. It is to be noted that in 3GPP UMTS network(s), gatewaynode(s) 1018 (e.g., GGSN) and tunnel interface (e.g., TTG) comprise apacket data gateway (PDG).

Macro network platform 1010 also includes serving node(s) 1016 thatconvey the various packetized flows of information or data streams,received through gateway node(s) 1018. As an example, in a 3GPP UMTSnetwork, serving node(s) can be embodied in serving GPRS support node(s)(SGSN).

As indicated above, server(s) 1014 in macro network platform 1010 canexecute numerous applications (e.g., location services, online gaming,wireless banking, wireless device management . . . ) that generatemultiple disparate packetized data streams or flows, and manage (e.g.,schedule, queue, format . . . ) such flows. Such application(s), forexample can include add-on features to standard services provided bymacro network platform 1010. Data streams can be conveyed to gatewaynode(s) 1018 for authorization/authentication and initiation of a datasession, and to serving node(s) 1016 for communication thereafter.Server(s) 1014 can also effect security (e.g., implement one or morefirewalls) of macro network platform 1010 to ensure network's operationand data integrity in addition to authorization and authenticationprocedures that CS gateway node(s) 1012 and gateway node(s) 1018 canenact. Moreover, server(s) 1014 can provision services from externalnetwork(s), e.g., WAN 1050, or Global Positioning System (GPS)network(s) (not shown). It is to be noted that server(s) 1014 caninclude one or more processor configured to confer at least in part thefunctionality of macro network platform 1010. To that end, the one ormore processor can execute code instructions stored in memory 1030, forexample.

In example wireless environment 1000, memory 1030 stores informationrelated to operation of macro network platform 1010. Information caninclude business data associated with subscribers; market plans andstrategies, e.g., promotional campaigns, business partnerships;operational data for mobile devices served through macro networkplatform; service and privacy policies; end-user service logs for lawenforcement; and so forth. Memory 1030 can also store information fromat least one of telephony network(s) 1040, WAN(s) 1050, or SS7 network1060, enterprise NW(s) 1065, or service NW(s) 1067.

Femto gateway node(s) 1084 have substantially the same functionality asPS gateway node(s) 1018. Additionally, femto gateway node(s) 1084 canalso include substantially all functionality of serving node(s) 1016. Inan aspect, femto gateway node(s) 1084 facilitates handover resolution,e.g., assessment and execution. Further, control node(s) 1020 canreceive handover requests and relay them to a handover component (notshown) via gateway node(s) 1084. According to an aspect, control node(s)1020 can support RNC capabilities.

Server(s) 1082 have substantially the same functionality as described inconnection with server(s) 1014. In an aspect, server(s) 1082 can executemultiple application(s) that provide service (e.g., voice and data) towireless devices served through femto RAN 1090. Server(s) 1082 can alsoprovide security features to femto network platform. In addition,server(s) 1082 can manage (e.g., schedule, queue, format . . . )substantially all packetized flows (e.g., IP-based, frame relay-based,ATM-based) it generates in addition to data received from macro networkplatform 1010. It is to be noted that server(s) 1082 can include one ormore processor configured to confer at least in part the functionalityof macro network platform 1010. To that end, the one or more processorcan execute code instructions stored in memory 1086, for example.

Memory 1086 can include information relevant to operation of the variouscomponents of femto network platform 1080. For example operationalinformation that can be stored in memory 1086 can comprise, but is notlimited to, subscriber information; contracted services; maintenance andservice records; femto cell configuration (e.g., devices served throughfemto RAN 1090; access control lists, or white lists); service policiesand specifications; privacy policies; add-on features; and so forth.

It is noted that femto network platform 1080 and macro network platform1010 can be functionally connected through one or more reference link(s)or reference interface(s). In addition, femto network platform 1080 canbe functionally coupled directly (not illustrated) to one or more ofexternal network(s) 1040, 1050, 1060, 1065 or 1067. Reference link(s) orinterface(s) can functionally link at least one of gateway node(s) 1084or server(s) 1086 to the one or more external networks 1040, 1050, 1060,1065 or 1067.

FIG. 11 illustrates a wireless environment that includes macro cells andfemtocells for wireless coverage in accordance with aspects describedherein. In wireless environment 1150, two areas 1105 represent “macro”cell coverage; each macro cell is served by a base station 1110. It canbe appreciated that macro cell coverage area 1105 and base station 1110can include functionality, as more fully described herein, for example,with regard to system 1100. Macro coverage is generally intended toserve mobile wireless devices, like UE 1120 _(A), 1120 _(B), in outdoorslocations. An over-the-air wireless link 115 provides such coverage, thewireless link 1215 comprises a downlink (DL) and an uplink (UL), andutilizes a predetermined band, licensed or unlicensed, of the radiofrequency (RF) spectrum. As an example, UE 1120 _(A), 1120 _(B) can be a3GPP Universal Mobile Telecommunication System (UMTS) mobile phone. Itis noted that a set of base stations, its associated electronics,circuitry or components, base stations control component(s), andwireless links operated in accordance to respective base stations in theset of base stations form a radio access network (RAN). In addition,base station 1110 communicates via backhaul link(s) 1151 with a macronetwork platform 1160, which in cellular wireless technologies (e.g.,3rd Generation Partnership Project (3GPP) Universal MobileTelecommunication System (UMTS), Global System for Mobile Communication(GSM)) represents a core network.

In an aspect, macro network platform 1160 controls a set of basestations 1110 that serve either respective cells or a number of sectorswithin such cells. Base station 1110 comprises radio equipment 1114 foroperation in one or more radio technologies, and a set of antennas 1112(e.g., smart antennas, microwave antennas, satellite dish(es) . . . )that can serve one or more sectors within a macro cell 1105. It is notedthat a set of radio network control node(s), which can be a part ofmacro network platform; a set of base stations (e.g., Node B 1110) thatserve a set of macro cells 1105; electronics, circuitry or componentsassociated with the base stations in the set of base stations; a set ofrespective OTA wireless links (e.g., links 1115 or 1116) operated inaccordance to a radio technology through the base stations; and backhaullink(s) 1155 and 1151 form a macro radio access network (RAN). Macronetwork platform 1160 also communicates with other base stations (notshown) that serve other cells (not shown). Backhaul link(s) 1151 or 1153can include a wired backbone link (e.g., optical fiber backbone,twisted-pair line, T1/E1 phone line, a digital subscriber line (DSL)either synchronous or asynchronous, an asymmetric ADSL, or a coaxialcable . . . ) or a wireless (e.g., line-of-sight (LOS) or non-LOS)backbone link. Backhaul pipe(s) 1155 link disparate base stations 1110.According to an aspect, backhaul link 1153 can connect multiple femtoaccess points 1130 and/or controller components (CC) 1101 to the femtonetwork platform 1102. In one example, multiple femto APs can beconnected to a routing platform (RP) 1087, which in turn can be connectto a controller component (CC) 1101. Typically, the information from UEs1120 _(A) can be routed by the RP 102, for example, internally, toanother UE 1120 _(A) connected to a disparate femto AP connected to theRP 1087, or, externally, to the femto network platform 1102 via the CC1101, as discussed in detail supra.

In wireless environment 1150, within one or more macro cell(s) 1105, aset of femtocells 1145 served by respective femto access points (APs)1130 can be deployed. It can be appreciated that, aspects of the subjectinnovation are geared to femtocell deployments with substantive femto APdensity, e.g., 10⁴-10⁷ femto APs 1130 per base station 1110. Accordingto an aspect, a set of femto access points 1130 ₁-3730 _(N), with N anatural number, can be functionally connected to a routing platform1087, which can be functionally coupled to a controller component 1101.The controller component 1101 can be operationally linked to the femtonetwork platform 330 by employing backhaul link(s) 1153. Accordingly,UEs UE 3720 _(A) connected to femto APs 1130 ₁-3830 _(N) can communicateinternally within the femto enterprise via the routing platform (RP)1087 and/or can also communicate with the femto network platform 1102via the RP 1087, controller component 1101 and the backhaul link(s)1153. It can be appreciated that although only one femto enterprise isdepicted in FIG. 11, multiple femto enterprise networks can be deployedwithin a macro cell 1105.

It is noted that while various aspects, features, or advantagesdescribed herein have been illustrated through femto access point(s) andassociated femto coverage, such aspects and features also can beexploited for home access point(s) (HAPs) that provide wireless coveragethrough substantially any, or any, disparate telecommunicationtechnologies, such as for example Wi-Fi (wireless fidelity) or picocelltelecommunication. Additionally, aspects, features, or advantages of thesubject innovation can be exploited in substantially any wirelesstelecommunication, or radio, technology; for example, Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), Enhanced General PacketRadio Service (Enhanced GPRS), 3GPP LTE, 3GPP2 UMB, 3GPP UMTS, HSPA,HSDPA, HSUPA, or LTE Advanced. Moreover, substantially all aspects ofthe subject innovation can include legacy telecommunicationtechnologies.

Referring now to FIG. 12, there is illustrated a block diagram of anexemplary computer system operable to execute the disclosedarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 12 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1200 in which the various aspects of the disclosedsubject matter can be implemented. Additionally, while the disclosedsubject matter described above may be suitable for application in thegeneral context of computer-executable instructions that may run on oneor more computers, those skilled in the art will recognize that thedisclosed subject matter also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the disclosed subject matter may also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

A computer typically includes a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the computer and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include eithervolatile or nonvolatile, removable and non-removable media implementedin any method or technology for storage of information such ascomputer-readable instructions, data structures, program modules orother data. Computer storage media includes, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

With reference again to FIG. 12, the exemplary environment 1200 forimplementing various aspects of the disclosed subject matter includes acomputer 1202, the computer 1202 including a processing unit 1204, asystem memory 1206 and a system bus 1208. The system bus 1208 couples tosystem components including, but not limited to, the system memory 1206to the processing unit 1204. The processing unit 1204 can be any ofvarious commercially available processors. Dual microprocessors andother multi-processor architectures may also be employed as theprocessing unit 1204.

The system bus 1208 can be any of several types of bus structure thatmay further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes read-only memory (ROM) 1210 and random access memory (RAM)1212. A basic input/output system (BIOS) is stored in a non-volatilememory 1210 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1202, such as during start-up. The RAM 1212 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1202 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), which internal hard disk drive 1214 may also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1216, (e.g., to read from or write to aremovable diskette 1218) and an optical disk drive 1220, (e.g., readinga CD-ROM disk 1222 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1214, magnetic diskdrive 1216 and optical disk drive 1220 can be connected to the systembus 1208 by a hard disk drive interface 1224, a magnetic disk driveinterface 1226 and an optical drive interface 1228, respectively. Theinterface 1224 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject matter disclosed herein.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1202, the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer, such as zipdrives, magnetic cassettes, flash memory cards, cartridges, and thelike, may also be used in the exemplary operating environment, andfurther, that any such media may contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. It is appreciated that the disclosed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 1202 throughone or more wired/wireless input devices, e.g., a keyboard 1238 and apointing device, such as a mouse 1240. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1242 that is coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1244 or other type of display device is also connected to thesystem bus 1208 via an interface, such as a video adapter 1246. Inaddition to the monitor 1244, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1202 may operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1248. The remotecomputer(s) 1248 can be a workstation, a server computer, a router, apersonal computer, a mobile device, portable computer,microprocessor-based entertainment appliance, a peer device or othercommon network node, and typically includes many or all of the elementsdescribed relative to the computer 1202, although, for purposes ofbrevity, only a memory/storage device 1250 is illustrated. The logicalconnections depicted include wired/wireless connectivity to a local areanetwork (LAN) 1252 and/or larger networks, e.g., a wide area network(WAN) 1254. Such LAN and WAN networking environments are commonplace inoffices and companies, and facilitate enterprise-wide computer networks,such as intranets, all of which may connect to a global communicationsnetwork, e.g., the Internet.

When used in a LAN networking environment, the computer 1202 isconnected to the local network 1252 through a wired and/or wirelesscommunication network interface or adapter 1256. The adapter 1256 mayfacilitate wired or wireless communication to the LAN 1252, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1256.

When used in a WAN networking environment, the computer 1202 can includea modem 1258, or is connected to a communications server on the WAN1254, or has other means for establishing communications over the WAN1254, such as by way of the Internet. The modem 1258, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1208 via the serial port interface 1242. In a networkedenvironment, program modules depicted relative to the computer 1202, orportions thereof, can be stored in the remote memory/storage device1250. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer 1202 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 5 GHz radio bands, at an 11Mbps (802.11b) or 54 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10 BaseT” wiredEthernet networks used in many offices.

Various aspects or features described herein can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. In addition, various aspects disclosed inthe subject specification can also be implemented through programmodules stored in a memory and executed by a processor, or othercombination of hardware and software, or hardware and firmware. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disc (CD), digitalversatile disc (DVD), blu-ray disc (BD) . . . ), smart cards, and flashmemory devices (e.g., card, stick, key drive . . . ). Additionally itshould be appreciated that a carrier wave can be employed to carrycomputer-readable electronic data such as those used in transmitting andreceiving electronic mail or in accessing a network such as the internetor a local area network (LAN). Of course, those skilled in the art willrecognize many modifications may be made to this configuration withoutdeparting from the scope or spirit of the disclosed subject matter.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan include various types of media that are readable by a computer, suchas hard-disc drives, zip drives, magnetic cassettes, flash memory cardsor other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory caninclude read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can include random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

What has been described above includes examples of the variousembodiments. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the embodiments, but one of ordinary skill in the art mayrecognize that many further combinations and permutations are possible.Accordingly, the detailed description is intended to embrace all suchalterations, modifications, and variations that fall within the spiritand scope of the appended claims.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the embodiments. In thisregard, it will also be recognized that the embodiments includes asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes,” and “including”and variants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

1. A system that facilitates support of disparate communicationsnetworks, comprising: a consolidated network repository (CNR) configuredas a single logical repository, comprising: a backend store thatmaintains data associated with multiple disparate communications networkplatforms; an interface component configured to support multiplecommunications network platform domains, wherein the interface componentreceives a request associated with an access to the backend store; and adata management component that receives the request, accesses thebackend store, and serves the request.
 2. The system of claim 1, theinterface component converts the request to a standardized requestaccording to a standard protocol expected by the data managementcomponent and independent of a domain type of requesting communicationsplatform; and the data management component receives the standardizedrequest.
 3. The system of claim 1, the multiple communications networkplatform domains include two or more of a wireless domain, a wirelinedomain, an Internet Protocol (IP) Multimedia Subsystem (IMS) domain, ora broadband domain.
 4. The system of claim 1, the interface componentincludes multiple frontend interfaces that facilitate the support of themultiple communications network platform domains.
 5. The system of claim4, the multiple frontend interfaces include two or more of (1) a HomeLocation Register (HLR) frontend, (2) a Home Subscriber Server (HSS)frontend, (3) an Authentication, Authorization, and Accounting (AAA)frontend, or (4) an application interface frontend.
 6. The system ofclaim 5, the HLR frontend employs Mobile Application Part (MAP) protocolto facilitate an interface to network elements configured according to awireless domain communication standard; the HSS frontend employsDIAMETER protocol to facilitate an interface to network elementsconfigured according to an IMS domain communication standard, the AAAfrontend employs either DIAMETER or Remote Authentication Dial In UserService (RADIUS) protocol to facilitate an interface to network elementsthat utilize one or more AAA-based application, and the applicationinterface frontend is configured to support at least one of AAA,Equipment Identity Register (EIR), Common Architecture for Real-TimeServices (CARTS), Lightweight Directory Access Protocol (LDAP), orApplication Server (AS).
 7. The system of claim 5, the multiple frontendinterfaces are data-less and support protocols including C, D, Cx, Dx,LDAP, Simple Object Access Protocol (SOAP), Extensible Markup Language(XML), Hypertext Transfer Protocol (HTTP), or Simple Network ManagementProtocol (SNMP).
 8. The system of claim 1, the data management componentconfigured to maintain a location index of data included in the backendstore of the CNR.
 9. The system of claim 8, the data managementcomponent includes at least one of an indexing component, a routingcomponent, a caching component a data adaption function (DAF) component,a notification component, or a SuM component.
 10. The system of claim 9,wherein at least one of (1) the indexing component or the routingcomponent configured to maintain the location index or to operate as asubscriber directory to all or a portion of frontend interfaces includedin the interface component, (2) the caching component configured totemporarily store data retrieved from the backend store, (3) the DAFcomponent configured to adapt data retrieved from the backend store fordata structures or data representations expected by an application thatoriginated the request, (4) the notification component configured tosubscribe or notify one or more of the multiple frontend interfacesincluded in the interface component of changes to data included in thebackend store, or (5) a SuM component configured to interface toprovisioning components or to coordinate updates associated with theCNR.
 11. The system of claim 1, the backend store includes multiple datarepositories configured to redundantly store the data associated withthe multiple disparate communications network platform.
 12. The systemof claim 11, the backend store configured with a common schema.
 13. Thesystem of claim 1, the CNR further comprising: a backend layer thatincludes multiple backend stores included in a first logical wide areanetwork (WAN); an interface layer that includes multiple interfacecomponents included in a second logical WAN; and a data management layerthat includes multiple data management components included in a thirdlogical WAN.
 14. The system of claim 13, the CNR is physicallydistributed among multiple geographic locations, wherein at least afirst portion of one or more layers included in the CNR resides at afirst geographic location and at least a second portion of the one ormore layers included in the CNR resides at a second geographic location.15. The system of claim 13, wherein at least one of (1) the multiplebackend stores included in the backend layer are networked via the firstlogical WAN such that a particular backend store included in the backendlayer is configured to communicate with other backend stores in ahorizontal fashion via the first logical WAN or with an associated datamanagement component in a vertical fashion; (2) the multiple interfacecomponents included in the interface layer are networked via the secondlogical WAN such that a particular interface component included in theinterface layer is configured to communicate with other interfacecomponents in a horizontal fashion via the second logical WAN or with anassociated data management component 120 in a vertical fashion; or (3)the multiple data management components included in the data managementlayer can be networked via the third logical WAN such that a particulardata management component included in data management layer can beconfigured to communicate with other data management components in ahorizontal fashion via third logical WAN or with an associated interfacecomponent or an associated backend store in a vertical fashion.
 16. Thesystem of claim 13, wherein at least one layer included in the CNR isconfigured to be independently extensible or updateable such that anextension or update to the at least one layer requires no associatedextension or update to other layers included in the CNR.
 17. A methodfor integrating multiple disparate communications network platforms,comprising: configuring a consolidated network repository (CNR) as asingle logical repository for multiple disparate communicationsnetworks; employing a physical storage device or facility as a backendlayer for the CNR; configuring the backend layer for maintaining dataassociated with the multiple disparate communications network domains;configuring an interface layer for the CNR for supporting accessrequests from the multiple disparate communications network domains;configuring a data management layer that operates as an intermediarybetween the interface layer and the backend layer; and receiving arequest associated with an access to the backend layer at the interfacelayer and forwarding the request to the data management layer.
 18. Themethod of claim 17, further comprising at least one of the followingacts: converting the request to a standardized request according to astandard protocol expected by the data management layer and independentof a domain type; configuring the CNR as the single logical repositoryfor two or more of a wireless domain, a wireline domain, an IMS domain,or a broadband domain; including in the interface layer multiplefrontends respectively adapted for interfacing with the multipledisparate communications network domains or applications associatedtherewith; utilizing the data management layer for maintaining alocation index for data included in the backend layer; or configuringthe backend layer with a common schema.
 19. The method of claim 17,further comprising at least one of the following acts: distributing theCNR over multiple geographic regions; including in the multiplegeographic regions at least one of a backend store associated with afirst logical WAN networking the backend layer, an interface componentassociated with a second logical WAN networking the interface layer, ora data management component associated with a third logical WANnetworking the data management layer; configuring at least one layer ofthe CNR for communicating in a horizontal manner via a single logicalWAN or in a vertical manner with one or more disparate layer at a samegeographic region; or configuring the at least one layer for independentextensibility or updateability.
 20. A consolidated network repository(CNR) system that facilitates support of disparate communicationsnetworks, comprising: a backend layer comprising multiple backend storesdistributed over multiple geographic regions, wherein at least onebackend store maintains data associated with multiple disparatecommunications network platforms and is configured to communicate withother backend stores included in the backend layer by way of a firstlogical wide area network (WAN); an interface layer comprising multipleinterface components distributed over the multiple geographic regions,wherein at least one interface component (1) is configured to supportmultiple communications network platform domains, (2) receives a requestassociated with an access to the at least one backend store, and (3) isconfigured to communicate with other interface components included inthe interface layer by way of a second logical WAN; and a datamanagement layer comprising multiple data management componentsdistributed over the multiple geographic regions, wherein at least onedata management component (1) receives the request, accesses the atleast one backend store, and serves the request, and (2) is configuredto communicate with other data management components included in thedata management layer by way of a third logical WAN.